-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-29302: Wider Tez session open scope should be guarded to prevent local resource leaks #6161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
c2f235b to
1cd40f6
Compare
1cd40f6 to
8e11ed8
Compare
8e11ed8 to
5cac81e
Compare
|
not about to handle this: no more useful contextual information can be added here than "hey, I caught this exception, cleaned up, and now re-throwing the session open failure exception" |
|
Changes makes sense to me, to cleanup scratch directory in case of exception before LGTM +1 (non-binding) |
ql/src/test/org/apache/hadoop/hive/ql/exec/tez/TestTezSessionState.java
Outdated
Show resolved
Hide resolved
… local resource leaks
5cac81e to
263aafa
Compare
ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezSessionState.java
Outdated
Show resolved
Hide resolved
deniskuzZ
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, minor comment
ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezSessionState.java
Outdated
Show resolved
Hide resolved
|



What changes were proposed in this pull request?
Encapsulate a wider code path in error-handling while opening a Tez session.
The point of the patch is nothing more than refactoring code to a separate method:
Why are the changes needed?
A scratch directory can leak if an exception is thrown after it’s created and resources have been placed into it.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test added.